Download Administering a SQL Database Infrastructure.70-764.PassLeader.2018-11-23.239q.vcex

Use sp_who3 to first view the current system load and to identify a session of interest. You should execute the query several times to identify which session id is most consuming teh system resources. Parameters sp_who3 null - who is active; sp_who3 1 or 'memory' - who is consuming the memory; sp_who3 2 or 'cpu' - who has cached plans that consumed the most cumulative CPU (top 10); sp_who3 3 or 'count' - who is connected and how many sessions it has; sp_who3 4 or 'idle' - who is idle that has open transactions; sp_who3 5 or 'tempdb' - who is running tasks that use tempdb (top 5); and, sp_who3 6 or 'block' - who is blocking.

How to: Rebuild an Index (SQL Server Management Studio)To rebuild an index In Object Explorer, connect to an instance of the SQL Server Database Engine and then expand that instance. Expand Databases, expand the database that contains the table with the specified index, and then expand Tables. Expand the table in which the index belongs and then expand Indexes. Right-click the index to rebuild and then click Rebuild. To start the rebuild operation, click OK. References: https://technet.microsoft.com/en-us/library/ms187874(v=sql.105).aspx

Activity Monitor displays information about SQL Server processes and how these processes affect the current instance of SQL Server. Activity Monitor is a tabbed document window with the following expandable and collapsible panes: Overview, Active User Tasks, Resource Waits, Data File I/O, and Recent Expensive Queries.The Activity User Tasks Pane shows information for active user connections to the instance, including the following column:* Login: The SQL Server login name under which the session is currently executing.The Recent Expensive Queries Pane shows information about the most expensive queries that have been run on the instance over the last 30 seconds, including the following column:* CPU (ms/sec): The rate of CPU use by the queryReferences: https://technet.microsoft.com/en-us/library/cc879320(v=sql.105).aspx

The data collector is a core component of the data collection platform for SQL Server 2017 and the tools that are provided by SQL Server. The data collector provides one central point for data collection across your database servers and applications. This collection point can obtain data from a variety of sources and is not limited to performance data

SQL Server Data Tools (SSDT) is a Microsoft Visual Studio environment for creating business intelligence solutions. SSDT features the Report Designer authoring environment, where you can open, modify, preview, save, and deploy Reporting Services paginated report definitions, shared data sources, shared datasets, and report parts. References: https://msdn.microsoft.com/en-us/library/hh272686(v=vs.103).aspx

Data Collector can gather performance information from multiple SQL Server instances and store it in a single repository. It has three built-in data collecting specifications (data collectors) designed to collect the most important performance metrics. The information collected by default is about disk usage, query statistics, and server activity. The Query Statistics data collection set collects information about query statistics, activity, execution plans and text on the SQL Server instance. Missing indexes can be found with the execution plans. References: https://www.sqlshack.com/sql-server-performance-monitoring-data-collector/

The sp_lock system stored procedure is packaged with SQL Server and will give you insight into the locks that are happening on your system. This procedure returns much of its information from the syslock info in the master database, which is a system table that contains information on all granted, converting, and waiting lock requests. Note: sp_lock will be removed in a future version of Microsoft SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use this feature. To obtain information about locks in the SQL Server Database Engine, use the sys.dm_tran_locks dynamic management view.sys.dm_tran_locks returns information about currently active lock manager resources in SQL Server 2008and later. Each row represents a currently active request to the lock manager for a lock that has been granted or is waiting to be granted. References: https://docs.microsoft.com/en-us/sql/relational-databases/system-stored-procedures/sp-lock-transact-sql

From scenario: Instance4 and Instance5 are not part of AG1. Instance4 is engaged in heavy read-write I/O. The recovery point objective of Instancse4 is 60 minutes. RecoveryPoint Objectives are commonly described as the amount of data that was lost during the outage and recovery period.References: http://sqlmag.com/blog/sql-server-recovery-time-objectives-and-recovery-point-objectives

One of the filegroup is read_only should be as it only need to be backup up once. Partial backups are useful whenever you want to exclude read-only filegroups. A partial backup resembles a full database backup, but a partial backup does not contain all the filegroups. Instead, for a read-write database, a partial backup contains the data in the primary filegroup, every read-write filegroup, and, optionally, one or more read-only files. A partial backup of a read-only database contains only the primary filegroup. From scenario: Instance1 experiences heavy read-write traffic. The instance hosts a database named OperationsMainthat is four terabytes (TB) in size. The database has multiple data files and filegroups. One of the filegroups is read_only and is half of the total database size.References: https://docs.microsoft.com/en-us/sql/relational-databases/backup-restore/partial-backups-sql-server